← previous blocknext block →recent activity
Analyzing
Block #97,827,710
18 transactions · 18 stateful · 2026-08-21 05:38:13 UTC
Parallelism
72/100
Blocked
33%
Avg conflicts / tx
0.61
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,827,710 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w06w17w08w19w010w111w212w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x968a856c…ddda
0x34b655…2a6f
6 touches
3 conflicts
0xa149f0ce…4d65
0x40c49f…2af0
4 touches
1 conflict
0xfcc819f8…fe51
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x29be38f0…7bb1
0x40c49f…2af0
4 touches
1 conflict
0x54ed504e…b6b4
0x40c49f…2af0
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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
3 conflicts on slot 0x968a856cea…69ddda
Audit this contract →
← previous block·next block →recent activity