← previous blocknext block →recent activity
Analyzing
Block #97,466,567
20 transactions · 18 stateful · 2026-08-19 23:06:43 UTC
Parallelism
65/100
Blocked
50%
Avg conflicts / tx
0.8
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #97,466,567 · 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
2w04w05w16w07w18w210w311w313w115w416w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x35c37635…11a6
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x286711a5…b3bf
0x34b655…2a6f
4 touches
1 conflict
0x52df67cf…f77b
0x34b655…2a6f
4 touches
1 conflict
0x586297c7…4187
0x34b655…2a6f
4 touches
1 conflict
0x62341e2a…2d78
0x34b655…2a6f
4 touches
1 conflict
0x68297b76…8e24
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 0x35c37635a4…5311a6
Audit this contract →
← previous block·next block →recent activity