← previous blocknext block →recent activity
Analyzing
Block #97,603,730
20 transactions · 19 stateful · 2026-08-20 10:39:26 UTC
Parallelism
70/100
Blocked
53%
Avg conflicts / tx
1.3
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,603,730 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w26w39w411w512w013w114w215w316w419w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc9d4fca…ecbf
0x34b655…2a6f
12 touches
15 conflicts
0xd17580f9…ece1
0x754704…b603
10 touches
10 conflicts
0xabe7f156…7814
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x2bde83b8…27f9
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xad862891…5d02
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
15 conflicts on slot 0xcc9d4fcadb…14ecbf
Audit this contract →
← previous block·next block →recent activity