← previous blocknext block →recent activity
Analyzing
Block #90,784,515
21 transactions · 20 stateful · 2026-07-27 13:32:51 UTC
Parallelism
71/100
Blocked
35%
Avg conflicts / tx
0.43
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #90,784,515 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w18w29w312w116w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x17e90565…d957
0xa6afd3…d132
4 touches
1 conflict
0xfc24540b…6463
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x0f7df08f…cad4
0xa6afd3…d132
4 touches
1 conflict
0x09cac653…86ba
0x34b655…2a6f
4 touches
1 conflict
0x0f556856…2916
0x34b655…2a6f
4 touches
1 conflict
0x2f68ff96…38a6
0x34b655…2a6f
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