← previous blocknext block →recent activity
Analyzing
Block #91,261,019
18 transactions · 15 stateful · 2026-07-29 05:31:08 UTC
Parallelism
67/100
Blocked
47%
Avg conflicts / tx
0.78
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #91,261,019 · 18 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
1w02w15w06w17w29w213w314w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0ab54c30…b88e
0x34b655…2a6f
10 touches
10 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x94de4d05…ad01
0x34b655…2a6f
4 touches
1 conflict
0xd30f9e74…d404
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
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 0x0ab54c30a6…82b88e
Audit this contract →
← previous block·next block →recent activity