← previous blocknext block →recent activity
Analyzing
Block #97,521,131
27 transactions · 21 stateful · 2026-08-20 03:41:28 UTC
Parallelism
81/100
Blocked
48%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,521,131 · 27 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w17w18w210w213w315w018w119w220w325w426w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x10ea2f1f…205b
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x35a814ce…cb25
0x34b655…2a6f
4 touches
1 conflict
0x54f7f60f…43cc
0x34b655…2a6f
4 touches
1 conflict
0x793aa64d…b09c
0x34b655…2a6f
4 touches
1 conflict
0x7d56b722…b022
0x34b655…2a6f
4 touches
1 conflict
0x80398c66…f3cc
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 0x10ea2f1f71…84205b
Audit this contract →
← previous block·next block →recent activity