← previous blocknext block →recent activity
Analyzing
Block #97,561,246
21 transactions · 19 stateful · 2026-08-20 07:04:23 UTC
Parallelism
81/100
Blocked
32%
Avg conflicts / tx
0.52
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,561,246 · 21 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
1w02w03w17w08w09w112w115w216w320w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0e2202c5…8058
0x34b655…2a6f
6 touches
3 conflicts
0x779cc2f3…fde1
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xbf0975a1…945e
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x737acb78…fce8
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
3 conflicts on slot 0x0e2202c559…228058
Audit this contract →
← previous block·next block →recent activity