← previous blocknext block →recent activity
Analyzing
Block #97,718,413
19 transactions · 19 stateful · 2026-08-20 20:26:30 UTC
Parallelism
74/100
Blocked
53%
Avg conflicts / tx
0.84
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,718,413 · 19 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
1w02w13w05w06w17w08w19w210w211w312w414w115w218w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x0efc210e…70ab
0x34b655…2a6f
6 touches
3 conflicts
0x84a77e2d…6b02
0x34b655…2a6f
6 touches
3 conflicts
0x5b9878ef…b17a
0x34b655…2a6f
6 touches
3 conflicts
0xc99adce2…f832
0x34b655…2a6f
6 touches
3 conflicts
0x2485eb03…5832
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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
6 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity