← previous blocknext block →recent activity
Analyzing
Block #91,440,663
15 transactions · 14 stateful · 2026-07-29 20:37:06 UTC
Parallelism
53/100
Blocked
50%
Avg conflicts / tx
1.47
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,440,663 · 15 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w16w07w18w29w310w413w514w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x0f2d78b1…7363
0x34b655…2a6f
4 touches
1 conflict
0x2188cc46…35a8
0x34b655…2a6f
4 touches
1 conflict
0x271dd4c8…eff0
0x34b655…2a6f
4 touches
1 conflict
0x69ae9434…2122
0x34b655…2a6f
4 touches
1 conflict
0x6bdd6387…7ffa
0x34b655…2a6f
4 touches
1 conflict
0x735f7df7…2f5b
0x34b655…2a6f
4 touches
1 conflict
0x8cd684d0…c3cb
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
21 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity