← previous blocknext block →recent activity
Analyzing
Block #97,512,737
26 transactions · 21 stateful · 2026-08-20 02:59:14 UTC
Parallelism
73/100
Blocked
33%
Avg conflicts / tx
0.58
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #97,512,737 · 26 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w08w011w112w214w315w016w422w524w625w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x54dfead0…c61c
0x34b655…2a6f
8 touches
6 conflicts
0x35c37635…11a6
0x34b655…2a6f
6 touches
3 conflicts
0xaf498679…7732
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x4f4bdabd…ffba
0x34b655…2a6f
4 touches
1 conflict
0x5f925d31…b1fe
0x34b655…2a6f
4 touches
1 conflict
0x799408f9…86f9
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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 0x54dfead061…64c61c
Audit this contract →
← previous block·next block →recent activity