← previous blocknext block →recent activity
Analyzing
Block #97,355,466
26 transactions · 24 stateful · 2026-08-19 13:23:18 UTC
Parallelism
69/100
Blocked
58%
Avg conflicts / tx
1.12
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #97,355,466 · 26 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w36w47w48w59w510w611w515w616w720w125w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf18906a6…d2e3
0x34b655…2a6f
10 touches
10 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001e
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002e
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21c5
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x40bc5adc…eda6
0x34b655…2a6f
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
10 conflicts on slot 0xf18906a60b…97d2e3
Audit this contract →
← previous block·next block →recent activity