← previous blocknext block →recent activity
Analyzing
Block #97,842,186
23 transactions · 21 stateful · 2026-08-21 06:51:30 UTC
Parallelism
83/100
Blocked
33%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,842,186 · 23 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
6w07w08w09w110w113w014w216w318w119w222w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec1d6663…6042
0x34b655…2a6f
8 touches
6 conflicts
0xde5c131f…da2c
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x8571fbdb…345a
0x34b655…2a6f
4 touches
1 conflict
0x681529b5…bacf
0x34b655…2a6f
4 touches
1 conflict
0x7ad63029…3405
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xc3e714d3…22c0
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 0xec1d6663f8…f86042
Audit this contract →
← previous block·next block →recent activity