← previous blocknext block →recent activity
Analyzing
Block #97,896,814
38 transactions · 27 stateful · 2026-08-21 11:33:28 UTC
Parallelism
84/100
Blocked
48%
Avg conflicts / tx
0.79
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,896,814 · 38 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
1w02w14w25w310w417w021w022w123w224w325w427w128w533w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0002
0x103de0…bb55
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x9f8bcec7…5178
0x34b655…2a6f
4 touches
1 conflict
0xde5c131f…da2c
0xa6afd3…d132
4 touches
1 conflict
0xb8dc136f…fb16
0xc8689a…ee79
4 touches
1 conflict
0x22e0cc1d…ad0d
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
15 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity