← previous blocknext block →recent activity
Analyzing
Block #97,558,453
21 transactions · 19 stateful · 2026-08-20 06:50:06 UTC
Parallelism
67/100
Blocked
42%
Avg conflicts / tx
0.71
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #97,558,453 · 21 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
1w05w06w07w18w29w310w412w513w614w620w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x728f999a…832f
0x34b655…2a6f
8 touches
6 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x6f6fc26c…3e34
0x34b655…2a6f
4 touches
1 conflict
0x886f7fe6…8b7a
0x34b655…2a6f
4 touches
1 conflict
0x9465204c…bf37
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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 0x728f999afb…4e832f
Audit this contract →
← previous block·next block →recent activity