← previous blocknext block →recent activity
Analyzing
Block #97,359,423
38 transactions · 31 stateful · 2026-08-19 13:43:45 UTC
Parallelism
84/100
Blocked
55%
Avg conflicts / tx
1.03
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,359,423 · 38 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
1w05w18w09w010w111w112w015w016w017w118w119w221w222w324w225w326w328w230w431w136w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d863b2f…bd28
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x80656e3b…9240
0x34b655…2a6f
8 touches
6 conflicts
0x8f1f2437…84c8
0xd32edf…ff58
7 touches
6 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0xe5e7089a…fb91
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
10 conflicts on slot 0x5d863b2fa9…a7bd28
Audit this contract →
← previous block·next block →recent activity