← previous blocknext block →recent activity
Analyzing
Block #97,396,846
17 transactions · 15 stateful · 2026-08-19 17:14:09 UTC
Parallelism
88/100
Blocked
33%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #97,396,846 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w06w19w010w011w112w114w015w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x6f6aa736…a698
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xdf8c628d…34f2
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x258fcaf5…2084
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity