← previous blocknext block →recent activity
Analyzing
Block #97,667,312
28 transactions · 25 stateful · 2026-08-20 16:05:59 UTC
Parallelism
86/100
Blocked
48%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,667,312 · 28 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
1w02w13w14w05w16w07w08w19w111w214w215w217w320w123w227w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3ee6fef1…c4ed
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x920c3701…3fac
0x34b655…2a6f
6 touches
3 conflicts
0x8f80e25f…fbfc
0xa6afd3…d132
6 touches
3 conflicts
0x083a8763…5a7c
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xd6bd849a…5597
0x2a68ba…90c5
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 0x3ee6fef16d…94c4ed
Audit this contract →
← previous block·next block →recent activity