← previous blocknext block →recent activity
Analyzing
Block #97,711,312
13 transactions · 13 stateful · 2026-08-20 19:50:30 UTC
Parallelism
69/100
Blocked
38%
Avg conflicts / tx
0.62
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,711,312 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w06w27w39w111w012w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9db64d13…fb98
0x34b655…2a6f
6 touches
3 conflicts
0x8f80e25f…fbfc
0xa6afd3…d132
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0xf5938cff…6608
0x34b655…2a6f
4 touches
1 conflict
0xfadc118d…5d64
0x34b655…2a6f
4 touches
1 conflict
0x422d5490…52d9
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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 0x9db64d13f5…6efb98
Audit this contract →
← previous block·next block →recent activity