← previous blocknext block →recent activity
Analyzing
Block #97,513,225
23 transactions · 19 stateful · 2026-08-20 03:01:42 UTC
Parallelism
74/100
Blocked
47%
Avg conflicts / tx
0.87
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,513,225 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w08w09w112w213w314w015w416w117w218w321w522w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xee6fedf4…2374
0x34b655…2a6f
6 touches
3 conflicts
0x3e3f27ce…580c
0x34b655…2a6f
6 touches
3 conflicts
0x107f84ba…8b0a
0x34b655…2a6f
6 touches
3 conflicts
0xd192f4ed…d7ec
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xe3684e08…c96a
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity