← previous blocknext block →recent activity
Analyzing
Block #97,493,635
20 transactions · 17 stateful · 2026-08-20 01:23:08 UTC
Parallelism
65/100
Blocked
41%
Avg conflicts / tx
1.3
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #97,493,635 · 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
2w03w04w08w09w110w211w314w415w516w619w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x25d909da…1722
0x34b655…2a6f
8 touches
6 conflicts
0xf7bfb5fd…cb38
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x40a9339c…6572
0x34b655…2a6f
4 touches
1 conflict
0x41bfea99…ac66
0x34b655…2a6f
4 touches
1 conflict
0x69196d53…b31c
0x34b655…2a6f
4 touches
1 conflict
0x6c0e32fc…a6ca
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
21 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity