← previous blocknext block →recent activity
Analyzing
Block #91,996,243
7 transactions · 7 stateful · 2026-07-31 19:12:02 UTC
Parallelism
71/100
Blocked
14%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #91,996,243 · 7 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbffde283…3385
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x054afe69…16e8
0x34b655…2a6f
2 touches
0 conflicts
0x18d306ad…d8f4
0x34b655…2a6f
2 touches
0 conflicts
0x1a69c7c5…09cc
0x34b655…2a6f
2 touches
0 conflicts
0x1e1f8d85…2092
0x34b655…2a6f
2 touches
0 conflicts
0x201d7cf1…f7f2
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 0xbffde283d8…c63385
Audit this contract →
← previous block·next block →recent activity