← previous blocknext block →recent activity
Analyzing
Block #97,684,030
10 transactions · 10 stateful · 2026-08-20 17:31:51 UTC
Parallelism
70/100
Blocked
40%
Avg conflicts / tx
0.6
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,684,030 · 10 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
1w02w04w15w26w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68c23664…74c4
0x34b655…2a6f
6 touches
3 conflicts
0x61a87a98…de3f
0x851145…3f07
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xac4259fe…a5df
0x851145…3f07
4 touches
1 conflict
0x1e10796e…6213
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xa9af9157…5a6e
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
3 conflicts on slot 0x68c2366471…c574c4
Audit this contract →
← previous block·next block →recent activity