← previous blocknext block →recent activity
Analyzing
Block #97,513,035
25 transactions · 23 stateful · 2026-08-20 03:00:44 UTC
Parallelism
76/100
Blocked
57%
Avg conflicts / tx
1.16
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,513,035 · 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
3w04w05w16w17w28w39w310w411w412w216w118w323w424w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1ba73d09…ba89
0x34b655…2a6f
10 touches
10 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xec7d120d…7084
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x88e771e8…7d4a
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xd0d3b728…1cd1
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 0x1ba73d0943…35ba89
Audit this contract →
← previous block·next block →recent activity