← previous blocknext block →recent activity
Analyzing
Block #97,733,819
20 transactions · 19 stateful · 2026-08-20 21:44:19 UTC
Parallelism
80/100
Blocked
42%
Avg conflicts / tx
0.75
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,733,819 · 20 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
1w02w13w04w15w07w010w211w112w213w117w018w319w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x6df5acad…7f75
0x34b655…2a6f
6 touches
3 conflicts
0x457c48f1…cdb1
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0000
0x0d73bf…be07
4 touches
1 conflict
0x00000000…0001
0x0d73bf…be07
4 touches
1 conflict
0x00000000…0003
0x0d73bf…be07
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4bfdcd51…9b58
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
6 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity