← previous blocknext block →recent activity
Analyzing
Block #97,656,935
19 transactions · 18 stateful · 2026-08-20 15:12:15 UTC
Parallelism
58/100
Blocked
44%
Avg conflicts / tx
1.26
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #97,656,935 · 19 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w15w26w37w48w09w010w517w618w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x47b2d2eb…8aa5
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x2495c7ab…b0ac
0x34b655…2a6f
4 touches
1 conflict
0x3b3a5945…10d0
0x34b655…2a6f
4 touches
1 conflict
0xeed0c5e8…de19
0x34b655…2a6f
4 touches
1 conflict
0x0ac81f35…832c
0x34b655…2a6f
4 touches
1 conflict
0xd800e635…b1d7
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
15 conflicts on slot 0x47b2d2eb24…af8aa5
Audit this contract →
← previous block·next block →recent activity