← previous blocknext block →recent activity
Analyzing
Block #91,959,541
17 transactions · 14 stateful · 2026-07-31 16:07:26 UTC
Parallelism
82/100
Blocked
21%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #91,959,541 · 17 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
1w02w14w05w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x06324e12…4fd3
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x57b02276…db3f
0x34b655…2a6f
4 touches
1 conflict
0xa8b8fbde…396d
0x34b655…2a6f
4 touches
1 conflict
0x2f3b486d…efda
0x34b655…2a6f
2 touches
0 conflicts
0x507215e0…cddd
0x34b655…2a6f
2 touches
0 conflicts
0x5e16782d…9479
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 0x06324e126f…294fd3
Audit this contract →
← previous block·next block →recent activity