← previous blocknext block →recent activity
Analyzing
Block #97,502,635
29 transactions · 27 stateful · 2026-08-20 02:08:24 UTC
Parallelism
90/100
Blocked
33%
Avg conflicts / tx
0.45
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,502,635 · 29 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w06w07w18w010w011w112w113w217w119w021w022w126w127w228w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x806c6904…3d63
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xa21e8abe…a7f1
0x34b655…2a6f
4 touches
1 conflict
0xa3c91855…d0df
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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
3 conflicts on slot 0x806c6904e3…af3d63
Audit this contract →
← previous block·next block →recent activity