← previous blocknext block →recent activity
Analyzing
Block #95,542,723
19 transactions · 19 stateful · 2026-08-13 05:03:14 UTC
Parallelism
79/100
Blocked
32%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,542,723 · 19 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
4w05w19w010w111w212w313w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x73da210e…4a9d
0x968279…9342
8 touches
6 conflicts
0x00000000…0006
0x968279…9342
8 touches
6 conflicts
0x276eb86e…daed
0x968279…9342
8 touches
6 conflicts
0x276eb86e…daee
0x968279…9342
8 touches
6 conflicts
0x276eb86e…daf0
0x968279…9342
8 touches
6 conflicts
0x73da210e…4a96
0x968279…9342
8 touches
6 conflicts
0x73da210e…4a97
0x968279…9342
8 touches
6 conflicts
0x73da210e…4a9a
0x968279…9342
8 touches
6 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
6 conflicts on slot 0x73da210e8f…2d4a9d
Audit this contract →
← previous block·next block →recent activity