← previous blocknext block →recent activity
Analyzing
Block #96,448,191
8 transactions · 7 stateful · 2026-08-16 08:59:00 UTC
Parallelism
63/100
Blocked
57%
Avg conflicts / tx
0.75
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,448,191 · 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
1w02w13w24w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd62829b…a1e5
0x968279…9342
6 touches
3 conflicts
0x00000000…0006
0x968279…9342
6 touches
3 conflicts
0x94f32182…c68e
0x968279…9342
6 touches
3 conflicts
0x94f32182…c68f
0x968279…9342
6 touches
3 conflicts
0x94f32182…c691
0x968279…9342
6 touches
3 conflicts
0xfd62829b…a1df
0x968279…9342
6 touches
3 conflicts
0xfd62829b…a1e0
0x968279…9342
6 touches
3 conflicts
0xfd62829b…a1e3
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 0xfd62829b22…e3a1e5
Audit this contract →
← previous block·next block →recent activity