← previous blocknext block →recent activity
Analyzing
Block #90,915,855
30 transactions · 17 stateful · 2026-07-28 00:33:45 UTC
Parallelism
87/100
Blocked
53%
Avg conflicts / tx
0.37
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,915,855 · 30 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w16w27w010w011w117w218w119w020w021w126w127w229w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xc782ec05…5bb2
0xa6afd3…d132
4 touches
1 conflict
0xd2c2c148…be25
0x065c9d…c394
4 touches
1 conflict
0x00000000…0002
0x48cba2…b48b
4 touches
1 conflict
0xa0d3faac…ae01
0x754704…b603
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xc6b1d981…1be2
0xa6afd3…d132
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity