← previous blocknext block →recent activity
Analyzing
Block #94,850,795
23 transactions · 19 stateful · 2026-08-10 18:48:33 UTC
Parallelism
74/100
Blocked
37%
Avg conflicts / tx
0.74
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,850,795 · 23 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
2w04w010w111w212w315w416w521w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x383472f3…bdbc
0x34b655…2a6f
10 touches
10 conflicts
0x0a0cecef…4ed0
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x525c7656…f891
0x34b655…2a6f
4 touches
1 conflict
0x7be3246e…f89f
0x34b655…2a6f
4 touches
1 conflict
0xc53799eb…d928
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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
10 conflicts on slot 0x383472f317…d0bdbc
Audit this contract →
← previous block·next block →recent activity