← previous blocknext block →recent activity
Analyzing
Block #97,495,815
20 transactions · 19 stateful · 2026-08-20 01:34:06 UTC
Parallelism
65/100
Blocked
47%
Avg conflicts / tx
1.15
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #97,495,815 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w16w07w28w29w310w011w413w414w515w619w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c0dcd35…3d69
0x34b655…2a6f
10 touches
10 conflicts
0xb5ad5cc8…b605
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x3315ffd1…722e
0x34b655…2a6f
6 touches
3 conflicts
0x59a84baf…4dfa
0x34b655…2a6f
6 touches
3 conflicts
0xef5959a3…2a2f
0x34b655…2a6f
6 touches
3 conflicts
0xcd93b2d2…30e6
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
10 conflicts on slot 0x6c0dcd35b3…323d69
Audit this contract →
← previous block·next block →recent activity