← previous blocknext block →recent activity
Analyzing
Block #96,602,320
17 transactions · 16 stateful · 2026-08-16 21:54:32 UTC
Parallelism
41/100
Blocked
56%
Avg conflicts / tx
2.47
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #96,602,320 · 17 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w510w611w712w814w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x31616f97…1acc
0x34b655…2a6f
10 touches
10 conflicts
0x4845d038…d3ec
0x34b655…2a6f
10 touches
10 conflicts
0x427c9fc4…5cee
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0x2c2db8e9…fdc7
0x34b655…2a6f
6 touches
3 conflicts
0xbcab7dbe…2825
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
28 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity