← previous blocknext block →recent activity
Analyzing
Block #97,558,627
28 transactions · 25 stateful · 2026-08-20 06:50:59 UTC
Parallelism
86/100
Blocked
44%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,558,627 · 28 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
2w03w04w15w07w09w010w011w112w214w116w017w018w119w220w321w122w124w025w127w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0xdf60b7d0…ac74
0x34b655…2a6f
4 touches
1 conflict
0xe098738f…9bbe
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0xce163d4f…b563
0xa6afd3…d132
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity