← previous blocknext block →recent activity
Analyzing
Block #97,818,702
18 transactions · 18 stateful · 2026-08-21 04:52:45 UTC
Parallelism
72/100
Blocked
22%
Avg conflicts / tx
0.28
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,818,702 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w07w19w212w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4de40a98…ee65
0x34b655…2a6f
6 touches
3 conflicts
0xe8108409…d385
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x525941ab…1a33
0x34b655…2a6f
4 touches
1 conflict
0x5e2cc3ff…c13e
0x34b655…2a6f
4 touches
1 conflict
0x7316dc00…c16a
0x34b655…2a6f
4 touches
1 conflict
0x793aa64d…b09c
0x34b655…2a6f
4 touches
1 conflict
0x793aa64d…b09d
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
3 conflicts on slot 0x4de40a988e…f8ee65
Audit this contract →
← previous block·next block →recent activity