← previous blocknext block →recent activity
Analyzing
Block #97,360,756
35 transactions · 27 stateful · 2026-08-19 13:50:36 UTC
Parallelism
69/100
Blocked
59%
Avg conflicts / tx
1.46
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #97,360,756 · 35 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w28w19w010w211w312w413w414w516w624w727w828w934w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51ec7a62…9ff5
0x34b655…2a6f
14 touches
21 conflicts
0xc6b604e6…5152
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xec85b41e…7c96
0x1b6862…e19c
6 touches
3 conflicts
0x37d710c8…45c1
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
21 conflicts on slot 0x51ec7a6257…f99ff5
Audit this contract →
← previous block·next block →recent activity