← previous blocknext block →recent activity
Analyzing
Block #96,796,313
20 transactions · 17 stateful · 2026-08-17 14:10:14 UTC
Parallelism
60/100
Blocked
47%
Avg conflicts / tx
0.7
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #96,796,313 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w28w39w410w512w118w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcdc582f…a65d
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x8cd684d0…c3cb
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xfc8cd993…5c11
0x34b655…2a6f
6 touches
3 conflicts
0x0b7c1c6b…0529
0x34b655…2a6f
6 touches
3 conflicts
0x4e58deff…c5d0
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0xbcdc582f54…41a65d
Audit this contract →
← previous block·next block →recent activity