← previous blocknext block →recent activity
Analyzing
Block #97,501,373
20 transactions · 19 stateful · 2026-08-20 02:02:04 UTC
Parallelism
85/100
Blocked
42%
Avg conflicts / tx
0.65
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,501,373 · 20 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w05w06w17w18w09w210w211w012w114w015w118w219w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xa21e8abe…a7f1
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x3f9a1b4b…664e
0x34b655…2a6f
4 touches
1 conflict
0x4381471a…9ac1
0x34b655…2a6f
4 touches
1 conflict
0xa4f6a0ed…6e25
0x34b655…2a6f
4 touches
1 conflict
0xa4f6a0ed…6e26
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity