← previous blocknext block →recent activity
Analyzing
Block #96,560,576
6 transactions · 6 stateful · 2026-08-16 18:24:34 UTC
Parallelism
67/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,560,576 · 6 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
4w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2d58a69f…6820
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xafb8e71e…9285
0x34b655…2a6f
4 touches
1 conflict
0xbe0ebfaa…1606
0x34b655…2a6f
4 touches
1 conflict
0xf7c661e2…011b
0x34b655…2a6f
4 touches
1 conflict
0x0bd1061b…6f3f
0x34b655…2a6f
2 touches
0 conflicts
0x147a1e75…aefb
0x34b655…2a6f
2 touches
0 conflicts
0x167de262…f61f
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 0x2d58a69f53…da6820
Audit this contract →
← previous block·next block →recent activity