← previous blocknext block →recent activity
Analyzing
Block #97,612,306
23 transactions · 19 stateful · 2026-08-20 11:23:09 UTC
Parallelism
78/100
Blocked
32%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,612,306 · 23 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
7w08w19w212w313w414w415w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xad525cb3…1b17
0x34b655…2a6f
8 touches
6 conflicts
0x0588dd3a…a58d
0x34b655…2a6f
6 touches
3 conflicts
0xba860fcc…24bf
0x34b655…2a6f
6 touches
3 conflicts
0x422d5490…52d9
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xfe848b5f…a000
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
6 conflicts on slot 0xad525cb34f…ad1b17
Audit this contract →
← previous block·next block →recent activity