← previous blocknext block →recent activity
Analyzing
Block #96,827,111
13 transactions · 12 stateful · 2026-08-17 16:45:09 UTC
Parallelism
69/100
Blocked
33%
Avg conflicts / tx
0.69
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,827,111 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w18w210w312w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa86351b8…2c5a
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0x1caf0c05…15ce
0x34b655…2a6f
4 touches
1 conflict
0x4175950a…1dfe
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x498d9ac9…cda5
0x34b655…2a6f
4 touches
1 conflict
0x4b92c351…ba92
0x34b655…2a6f
4 touches
1 conflict
0x6ece1ea0…f6f4
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 0xa86351b861…d52c5a
Audit this contract →
← previous block·next block →recent activity