← previous blocknext block →recent activity
Analyzing
Block #97,368,023
17 transactions · 17 stateful · 2026-08-19 14:27:56 UTC
Parallelism
71/100
Blocked
53%
Avg conflicts / tx
1.06
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,368,023 · 17 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
1w02w13w24w05w16w07w28w09w110w313w314w415w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x70cfbacf…5c46
0x34b655…2a6f
8 touches
6 conflicts
0x1de88838…a293
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002e
0x1b6862…e19c
6 touches
3 conflicts
0x93afca4c…b47e
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x4360b49f…140d
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 0x70cfbacfa4…e85c46
Audit this contract →
← previous block·next block →recent activity