← previous blocknext block →recent activity
Analyzing
Block #91,437,822
9 transactions · 8 stateful · 2026-07-29 20:22:48 UTC
Parallelism
67/100
Blocked
25%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,437,822 · 9 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
1w02w14w08w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x0ab54c30…b88e
0x34b655…2a6f
4 touches
1 conflict
0x849c2133…33c6
0x34b655…2a6f
4 touches
1 conflict
0x282b6dca…fc80
0x34b655…2a6f
2 touches
0 conflicts
0x478e71ff…6cc6
0x34b655…2a6f
2 touches
0 conflicts
0x48108def…d9c1
0x34b655…2a6f
2 touches
0 conflicts
0x5939780d…8d2a
0x34b655…2a6f
2 touches
0 conflicts
0x757b0543…e087
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity