← previous blocknext block →recent activity
Analyzing
Block #96,797,513
26 transactions · 23 stateful · 2026-08-17 14:16:16 UTC
Parallelism
85/100
Blocked
26%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,797,513 · 26 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
1w03w06w07w112w214w015w118w119w024w225w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2f1de8d9…dbad
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x3e6302c8…64f5
0x34b655…2a6f
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x02d895f0…2b93
0x34b655…2a6f
4 touches
1 conflict
0x1b78ec69…0ce1
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
3 conflicts on slot 0x2f1de8d987…66dbad
Audit this contract →
← previous block·next block →recent activity