← previous blocknext block →recent activity
Analyzing
Block #97,552,584
27 transactions · 26 stateful · 2026-08-20 06:20:06 UTC
Parallelism
81/100
Blocked
62%
Avg conflicts / tx
1.26
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,552,584 · 27 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
1w02w03w15w06w18w09w110w111w212w213w114w315w316w420w426w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc38a1e34…37c3
0x34b655…2a6f
10 touches
10 conflicts
0x0a87cc63…5b91
0x34b655…2a6f
8 touches
6 conflicts
0x59a84baf…4dfa
0x34b655…2a6f
6 touches
3 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xe2457683…1957
0xa6afd3…d132
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x6e6d785f…51bb
0x34b655…2a6f
6 touches
3 conflicts
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
10 conflicts on slot 0xc38a1e3492…2d37c3
Audit this contract →
← previous block·next block →recent activity