← previous blocknext block →recent activity
Analyzing
Block #91,809,387
24 transactions · 24 stateful · 2026-07-31 03:32:00 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.71
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,809,387 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w16w28w19w311w212w313w415w016w521w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x98c396c0…fc95
0x34b655…2a6f
8 touches
6 conflicts
0xa1ff0729…0146
0xa6afd3…d132
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xb9834665…e363
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xa47b7766…ee6e
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
6 conflicts on slot 0x98c396c0a4…86fc95
Audit this contract →
← previous block·next block →recent activity