← previous blocknext block →recent activity
Analyzing
Block #97,664,852
22 transactions · 19 stateful · 2026-08-20 15:53:17 UTC
Parallelism
73/100
Blocked
53%
Avg conflicts / tx
0.77
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,664,852 · 22 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
1w05w06w17w28w29w311w412w513w115w116w221w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x157b6348…8604
0x34b655…2a6f
8 touches
6 conflicts
0xe429e4c9…9510
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x71cd5bd2…8c51
0x34b655…2a6f
4 touches
1 conflict
0x84720232…c5d1
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
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 0x157b634872…098604
Audit this contract →
← previous block·next block →recent activity