← previous blocknext block →recent activity
Analyzing
Block #96,126,101
14 transactions · 13 stateful · 2026-08-15 05:59:01 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,126,101 · 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
1w02w13w04w16w27w08w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb16c7748…d783
0x968279…9342
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x542e84ae…74d5
0x968279…9342
6 touches
3 conflicts
0x542e84ae…74d6
0x968279…9342
6 touches
3 conflicts
0x542e84ae…74d8
0x968279…9342
6 touches
3 conflicts
0xb16c7748…d77c
0x968279…9342
6 touches
3 conflicts
0xb16c7748…d77d
0x968279…9342
6 touches
3 conflicts
0xb16c7748…d780
0x968279…9342
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 0xb16c774879…d0d783
Audit this contract →
← previous block·next block →recent activity