← previous blocknext block →recent activity
Analyzing
Block #97,819,548
21 transactions · 19 stateful · 2026-08-21 04:57:02 UTC
Parallelism
81/100
Blocked
37%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,819,548 · 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
2w05w06w17w28w311w012w115w116w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7975e059…379b
0x34b655…2a6f
8 touches
6 conflicts
0x3cd6f7af…4a43
0xa6afd3…d132
4 touches
1 conflict
0x58e16b8d…8dad
0x34b655…2a6f
4 touches
1 conflict
0x921893c3…b9b6
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xebfa6e11…8be5
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 0x7975e0597e…c8379b
Audit this contract →
← previous block·next block →recent activity