← previous blocknext block →recent activity
Analyzing
Block #97,500,116
20 transactions · 18 stateful · 2026-08-20 01:55:44 UTC
Parallelism
80/100
Blocked
28%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,500,116 · 20 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
1w02w05w07w08w19w210w112w014w319w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x886f7fe6…8b7a
0x34b655…2a6f
8 touches
6 conflicts
0x728f999a…832f
0x34b655…2a6f
4 touches
1 conflict
0x246e5638…b635
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0xa21e8abe…a7f1
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0028
0x1b6862…e19c
2 touches
0 conflicts
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 0x886f7fe654…c88b7a
Audit this contract →
← previous block·next block →recent activity