← previous blocknext block →recent activity
Analyzing
Block #91,542,310
19 transactions · 15 stateful · 2026-07-30 05:08:31 UTC
Parallelism
68/100
Blocked
47%
Avg conflicts / tx
0.74
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,542,310 · 19 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
5w06w17w212w213w314w416w517w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e1faa73…bfbf
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xddd7607e…9b4b
0x34b655…2a6f
6 touches
3 conflicts
0xbbeac3b7…c14b
0x34b655…2a6f
6 touches
3 conflicts
0xc0ab38cc…600c
0x34b655…2a6f
6 touches
3 conflicts
0x36a6e1a0…4d87
0x34b655…2a6f
4 touches
1 conflict
0x4e068769…91ad
0x34b655…2a6f
4 touches
1 conflict
0x67905f6e…02a1
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
6 conflicts on slot 0x7e1faa73db…84bfbf
Audit this contract →
← previous block·next block →recent activity