← previous blocknext block →recent activity
Analyzing
Block #97,826,190
14 transactions · 14 stateful · 2026-08-21 05:30:34 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,826,190 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w08w210w313w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0eccef84…202d
0x34b655…2a6f
8 touches
6 conflicts
0xa242e227…2e45
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0x055142b6…16b8
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x44e7b8f0…96e9
0x34b655…2a6f
4 touches
1 conflict
0x95ac2b0f…61e2
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
6 conflicts on slot 0x0eccef8488…7b202d
Audit this contract →
← previous block·next block →recent activity