← previous blocknext block →recent activity
Analyzing
Block #91,294,685
9 transactions · 6 stateful · 2026-07-29 08:21:17 UTC
Parallelism
78/100
Blocked
17%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,294,685 · 9 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x0ab54c30…b88e
0x34b655…2a6f
4 touches
1 conflict
0x0d6d262c…958d
0x34b655…2a6f
2 touches
0 conflicts
0x27772642…321a
0x34b655…2a6f
2 touches
0 conflicts
0x2d93071a…5ba7
0x34b655…2a6f
2 touches
0 conflicts
0x2dfde2ed…8801
0x34b655…2a6f
2 touches
0 conflicts
0x3a15404b…10b1
0x34b655…2a6f
2 touches
0 conflicts
0x5e4b65e1…ebe1
0x34b655…2a6f
2 touches
0 conflicts
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 0xe5bb3628b5…71e5f1
Audit this contract →
← previous block·next block →recent activity