← previous blocknext block →recent activity
Analyzing
Block #97,718,392
11 transactions · 11 stateful · 2026-08-20 20:26:24 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,718,392 · 11 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
2w04w05w16w27w310w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8afd9c1b…9c0f
0x34b655…2a6f
8 touches
6 conflicts
0x5b9878ef…b17a
0x34b655…2a6f
8 touches
6 conflicts
0x232b0b19…d946
0x34b655…2a6f
6 touches
3 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x62e1238c…cad0
0x34b655…2a6f
3 touches
1 conflict
0xd61a7c18…9f3e
0x065c9d…c394
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
6 conflicts on slot 0x8afd9c1b8f…279c0f
Audit this contract →
← previous block·next block →recent activity