← previous blocknext block →recent activity
Analyzing
Block #91,405,802
20 transactions · 16 stateful · 2026-07-29 17:40:34 UTC
Parallelism
80/100
Blocked
38%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,405,802 · 20 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
3w04w06w17w28w310w011w112w318w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb92274b7…214a
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x6e6b8ec7…2197
0x34b655…2a6f
4 touches
1 conflict
0x8f681fbd…db30
0x34b655…2a6f
4 touches
1 conflict
0x98459f89…575d
0x34b655…2a6f
4 touches
1 conflict
0xbbeac3b7…c14b
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
6 conflicts on slot 0xb92274b7fb…4c214a
Audit this contract →
← previous block·next block →recent activity