← previous blocknext block →recent activity
Analyzing
Block #97,515,509
25 transactions · 21 stateful · 2026-08-20 03:13:11 UTC
Parallelism
68/100
Blocked
48%
Avg conflicts / tx
1.12
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #97,515,509 · 25 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
1w05w06w17w28w09w310w111w412w513w615w616w724w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5553f577…f9ee
0x34b655…2a6f
10 touches
10 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
8 touches
6 conflicts
0xec7d120d…7084
0x34b655…2a6f
8 touches
6 conflicts
0xedb36e17…7e26
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x55e10744…f4f8
0x34b655…2a6f
4 touches
1 conflict
0x6bba3e23…e208
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
10 conflicts on slot 0x5553f5776f…6df9ee
Audit this contract →
← previous block·next block →recent activity