← previous blocknext block →recent activity
Analyzing
Block #97,546,486
19 transactions · 16 stateful · 2026-08-20 05:49:00 UTC
Parallelism
84/100
Blocked
31%
Avg conflicts / tx
0.42
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,546,486 · 19 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w06w17w09w011w012w113w114w218w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd4629028…4cf2
0x34b655…2a6f
6 touches
3 conflicts
0xb64473b0…0d6f
0xc8689a…ee79
4 touches
1 conflict
0xb97c885b…2933
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xf7bfb5fd…cb38
0x34b655…2a6f
4 touches
1 conflict
0xf9a57445…8ac2
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
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
3 conflicts on slot 0xd4629028cb…b64cf2
Audit this contract →
← previous block·next block →recent activity