← previous blocknext block →recent activity
Analyzing
Block #96,275,986
8 transactions · 6 stateful · 2026-08-15 18:32:55 UTC
Parallelism
63/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,275,986 · 8 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf30b9357…2e1e
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xad843ea4…ad90
0x34b655…2a6f
4 touches
1 conflict
0x28e5dbea…2f7f
0x34b655…2a6f
4 touches
1 conflict
0x763104af…f44e
0x34b655…2a6f
4 touches
1 conflict
0x109d18b7…997d
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
3 conflicts on slot 0xf30b935720…582e1e
Audit this contract →
← previous block·next block →recent activity