← previous blocknext block →recent activity
Analyzing
Block #96,112,198
15 transactions · 14 stateful · 2026-08-15 04:49:04 UTC
Parallelism
73/100
Blocked
29%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,112,198 · 15 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
5w06w17w28w311w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xf1e2b312…464f
0x968279…9342
4 touches
1 conflict
0xf1e2b312…4649
0x968279…9342
4 touches
1 conflict
0xf1e2b312…464a
0x968279…9342
4 touches
1 conflict
0xf1e2b312…464d
0x968279…9342
4 touches
1 conflict
0xf1e2b312…464e
0x968279…9342
4 touches
1 conflict
0x09396f14…669f
0x34b655…2a6f
4 touches
1 conflict
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: Perpl
6 conflicts on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity