← previous blocknext block →recent activity
Analyzing
Block #97,996,554
25 transactions · 19 stateful · 2026-08-21 20:00:30 UTC
Parallelism
88/100
Blocked
37%
Avg conflicts / tx
0.32
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,996,554 · 25 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
6w07w08w19w012w013w118w119w121w222w224w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa7ecbbe7…f713
0x34b655…2a6f
6 touches
3 conflicts
0xe9b84e94…cc05
0x40c49f…2af0
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd9c075c9…0a14
0x34b655…2a6f
4 touches
1 conflict
0xe2bf267f…6b8c
0x34b655…2a6f
4 touches
1 conflict
0xff7657e6…a4b7
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0xc51a9e5e…6f84
0x40c49f…2af0
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 0xa7ecbbe767…04f713
Audit this contract →
← previous block·next block →recent activity