← previous blocknext block →recent activity
Analyzing
Block #97,670,560
20 transactions · 20 stateful · 2026-08-20 16:22:38 UTC
Parallelism
65/100
Blocked
40%
Avg conflicts / tx
0.7
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #97,670,560 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w26w38w09w411w512w614w115w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3df3de0d…cd8b
0x34b655…2a6f
8 touches
6 conflicts
0x1bc9b1ca…85ef
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x43357924…e89d
0x34b655…2a6f
6 touches
3 conflicts
0xac4259fe…a5df
0x851145…3f07
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x6f6fc26c…3e34
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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 0x3df3de0dae…bccd8b
Audit this contract →
← previous block·next block →recent activity