← previous blocknext block →recent activity
Analyzing
Block #97,729,604
30 transactions · 27 stateful · 2026-08-20 21:23:07 UTC
Parallelism
87/100
Blocked
37%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,729,604 · 30 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
3w04w05w06w07w08w19w110w211w112w213w114w215w328w129w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x69352f9f…5449
0x34b655…2a6f
6 touches
3 conflicts
0xfaab1754…53be
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xacbe889e…944d
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…002d
0x1b6862…e19c
4 touches
1 conflict
0x6d43ee99…bdd8
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x06a27525…f082
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 0x69352f9f62…375449
Audit this contract →
← previous block·next block →recent activity