← previous blocknext block →recent activity
Analyzing
Block #97,709,391
13 transactions · 12 stateful · 2026-08-20 19:40:48 UTC
Parallelism
69/100
Blocked
25%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,709,391 · 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
5w08w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaab1754…53be
0x34b655…2a6f
8 touches
6 conflicts
0xe9a3a799…fa58
0x34b655…2a6f
4 touches
1 conflict
0xe75ce681…ba60
0x188d58…ea8e
2 touches
0 conflicts
0x3a921be0…779c
0x2a68ba…90c5
2 touches
0 conflicts
0x0505bae8…b4fb
0x34b655…2a6f
2 touches
0 conflicts
0x2f5c6ab7…20ab
0x34b655…2a6f
2 touches
0 conflicts
0x5c1a0181…5d52
0x34b655…2a6f
2 touches
0 conflicts
0x68c23664…74c4
0x34b655…2a6f
2 touches
0 conflicts
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 0xfaab175490…2353be
Audit this contract →
← previous block·next block →recent activity