← previous blocknext block →recent activity
Analyzing
Block #97,500,701
14 transactions · 14 stateful · 2026-08-20 01:58:41 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,500,701 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w18w29w310w413w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0099420d…37b4
0x34b655…2a6f
10 touches
10 conflicts
0xaeb2ebc7…a48c
0x34b655…2a6f
6 touches
3 conflicts
0x9ac5e970…e945
0x34b655…2a6f
4 touches
1 conflict
0xfaf89f45…ced6
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x4188cc5f…2d2e
0x34b655…2a6f
2 touches
0 conflicts
0x881f8c35…f946
0x34b655…2a6f
2 touches
0 conflicts
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 0x0099420dea…e337b4
Audit this contract →
← previous block·next block →recent activity