← previous blocknext block →recent activity
Analyzing
Block #96,686,119
12 transactions · 10 stateful · 2026-08-17 04:55:59 UTC
Parallelism
50/100
Blocked
50%
Avg conflicts / tx
1.25
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,686,119 · 12 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w26w38w49w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x8075c973…5011
0x34b655…2a6f
6 touches
3 conflicts
0x3703b3c0…5695
0x34b655…2a6f
6 touches
3 conflicts
0x1e2bd3ed…19a2
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0xe8eae8a3…bacc
0x34b655…2a6f
6 touches
3 conflicts
0x70986451…c6bd
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity