← previous blocknext block →recent activity
Analyzing
Block #90,031,284
17 transactions · 16 stateful · 2026-07-24 22:03:52 UTC
Parallelism
76/100
Blocked
31%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #90,031,284 · 17 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
2w03w04w18w110w212w314w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x06726618…fafd
0x34b655…2a6f
6 touches
3 conflicts
0xc5031114…58ac
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x45ea7a97…bbb3
0x34b655…2a6f
6 touches
3 conflicts
0xcae19fc1…f8fa
0x851145…3f07
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x79bdf655…91f2
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 0x06726618f7…29fafd
Audit this contract →
← previous block·next block →recent activity