← previous blocknext block →recent activity
Analyzing
Block #97,738,953
25 transactions · 23 stateful · 2026-08-20 22:10:09 UTC
Parallelism
76/100
Blocked
48%
Avg conflicts / tx
0.84
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,738,953 · 25 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
1w02w14w05w16w17w28w09w010w111w212w215w019w320w223w424w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x69352f9f…5449
0x34b655…2a6f
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002d
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21c4
0x1b6862…e19c
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 0x69352f9f62…375449
Audit this contract →
← previous block·next block →recent activity