← previous blocknext block →recent activity
Analyzing
Block #97,558,503
17 transactions · 16 stateful · 2026-08-20 06:50:22 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #97,558,503 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w07w011w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0e350896…34d8
0x34b655…2a6f
4 touches
1 conflict
0x8a06d70a…8ba3
0x34b655…2a6f
4 touches
1 conflict
0x9e2cb5a0…bf4f
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x31ef4e0d…2944
0x34b655…2a6f
2 touches
0 conflicts
0x446ae419…e506
0x34b655…2a6f
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
1 conflict on slot 0x0e3508968e…7d34d8
Audit this contract →
← previous block·next block →recent activity