← previous blocknext block →recent activity
Analyzing
Block #97,519,386
19 transactions · 18 stateful · 2026-08-20 03:32:42 UTC
Parallelism
63/100
Blocked
56%
Avg conflicts / tx
1.05
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #97,519,386 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w06w27w08w110w211w312w315w416w517w618w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xf0eb12c6…a2b7
0x34b655…2a6f
6 touches
3 conflicts
0xce827910…ff22
0x065c9d…c394
6 touches
3 conflicts
0x353a3a00…5e0a
0x34b655…2a6f
4 touches
1 conflict
0x388f889f…a655
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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
10 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity