← previous blocknext block →recent activity
Analyzing
Block #91,260,029
10 transactions · 9 stateful · 2026-07-29 05:26:09 UTC
Parallelism
70/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,260,029 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9937c4f0…1cc4
0x34b655…2a6f
4 touches
1 conflict
0xbba9dcbb…e4c9
0x34b655…2a6f
4 touches
1 conflict
0x41827e21…a21c
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0xf854759f…202a
0x34b655…2a6f
4 touches
1 conflict
0x02878015…aba9
0x34b655…2a6f
4 touches
1 conflict
0x4fc141d9…bb36
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
1 conflict on slot 0x9937c4f09e…6c1cc4
Audit this contract →
← previous block·next block →recent activity