← previous blocknext block →recent activity
Analyzing
Block #95,972,288
16 transactions · 14 stateful · 2026-08-14 17:05:13 UTC
Parallelism
69/100
Blocked
57%
Avg conflicts / tx
0.94
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,972,288 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w16w29w010w111w212w313w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5ef8ccec…2138
0x968279…9342
8 touches
6 conflicts
0x49f95c4d…fc09
0x968279…9342
8 touches
6 conflicts
0x49f95c4d…fc0a
0x968279…9342
8 touches
6 conflicts
0x49f95c4d…fc0c
0x968279…9342
8 touches
6 conflicts
0x5ef8ccec…2131
0x968279…9342
8 touches
6 conflicts
0x5ef8ccec…2132
0x968279…9342
8 touches
6 conflicts
0x5ef8ccec…2135
0x968279…9342
8 touches
6 conflicts
0x5ef8ccec…2136
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 0x5ef8ccec5e…d42138
Audit this contract →
← previous block·next block →recent activity