← previous blocknext block →recent activity
Analyzing
Block #97,525,071
22 transactions · 19 stateful · 2026-08-20 04:01:17 UTC
Parallelism
77/100
Blocked
63%
Avg conflicts / tx
1.14
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,525,071 · 22 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
1w02w14w06w08w19w110w211w212w313w415w218w219w320w421w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x25ff7717…d4af
0x34b655…2a6f
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 conflicts
0x002fed35…79fa
0x2a68ba…90c5
8 touches
6 conflicts
0xa93d1e42…6c7f
0x065c9d…c394
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 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 0x25ff77178c…2ad4af
Audit this contract →
← previous block·next block →recent activity