← previous blocknext block →recent activity
Analyzing
Block #91,024,347
11 transactions · 10 stateful · 2026-07-28 09:40:21 UTC
Parallelism
64/100
Blocked
40%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #91,024,347 · 11 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
2w03w14w25w310w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbbeac3b7…c14b
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xddc0f050…9726
0x34b655…2a6f
4 touches
1 conflict
0x1a0e5f4b…849d
0x34b655…2a6f
4 touches
1 conflict
0x37da811a…f7dc
0x34b655…2a6f
4 touches
1 conflict
0x88e771e8…7d4a
0x34b655…2a6f
4 touches
1 conflict
0x9232202b…bc7e
0x34b655…2a6f
4 touches
1 conflict
0xa3a82eeb…dfb5
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 0xbbeac3b703…d0c14b
Audit this contract →
← previous block·next block →recent activity