← previous blocknext block →recent activity
Analyzing
Block #97,567,861
20 transactions · 20 stateful · 2026-08-20 07:38:09 UTC
Parallelism
70/100
Blocked
40%
Avg conflicts / tx
0.7
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,567,861 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w06w17w28w312w113w314w415w519w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x8b75c189…e32d
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xea1d91a3…b583
0x34b655…2a6f
6 touches
3 conflicts
0x015a51cb…b7b7
0x34b655…2a6f
4 touches
1 conflict
0x7a95dc7c…5870
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe283e878…7262
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
6 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity