← previous blocknext block →recent activity
Analyzing
Block #97,558,100
21 transactions · 20 stateful · 2026-08-20 06:48:17 UTC
Parallelism
62/100
Blocked
50%
Avg conflicts / tx
0.9
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #97,558,100 · 21 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w07w18w29w210w311w412w513w614w117w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x728f999a…832f
0x34b655…2a6f
8 touches
6 conflicts
0x6737ee07…9978
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xce163d4f…b563
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0002
0x103de0…bb55
4 touches
1 conflict
0x157e8320…c3b8
0x34b655…2a6f
4 touches
1 conflict
0x9465204c…bf37
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 0x728f999afb…4e832f
Audit this contract →
← previous block·next block →recent activity