← previous blocknext block →recent activity
Analyzing
Block #96,112,187
18 transactions · 17 stateful · 2026-08-15 04:49:01 UTC
Parallelism
83/100
Blocked
24%
Avg conflicts / tx
0.28
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,112,187 · 18 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
1w02w15w07w18w09w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 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
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x29c1a140…099f
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
3 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity