← previous blocknext block →recent activity
Analyzing
Block #91,797,865
14 transactions · 13 stateful · 2026-07-31 02:34:02 UTC
Parallelism
86/100
Blocked
31%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,797,865 · 14 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
1w02w13w04w06w18w19w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x2fd12b6c…02cc
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x890a1db9…1712
0xa6afd3…d132
4 touches
1 conflict
0xa1ff0729…0146
0xa6afd3…d132
4 touches
1 conflict
0xdb9ce9db…7bf5
0xa6afd3…d132
3 touches
1 conflict
0xef8ace5c…7578
0xa6afd3…d132
3 touches
1 conflict
0x8f4d2228…0578
0xd32edf…ff58
3 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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity