← previous blocknext block →recent activity
Analyzing
Block #96,219,254
14 transactions · 13 stateful · 2026-08-15 13:47:34 UTC
Parallelism
79/100
Blocked
46%
Avg conflicts / tx
0.64
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,219,254 · 14 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
1w02w13w26w08w19w010w111w212w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf53bf04a…d2a5
0x968279…9342
6 touches
3 conflicts
0x8718f3fa…a776
0x968279…9342
6 touches
3 conflicts
0x8718f3fa…a779
0x968279…9342
6 touches
3 conflicts
0x8718f3fa…a77a
0x968279…9342
6 touches
3 conflicts
0x8718f3fa…a77c
0x968279…9342
6 touches
3 conflicts
0xf53bf04a…d2a2
0x968279…9342
6 touches
3 conflicts
0xf53bf04a…d2a3
0x968279…9342
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
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: 0x96827978…f09342
3 conflicts on slot 0xf53bf04a8b…1cd2a5
Audit this contract →
← previous block·next block →recent activity