← previous blocknext block →recent activity
Analyzing
Block #97,738,276
18 transactions · 17 stateful · 2026-08-20 22:06:45 UTC
Parallelism
72/100
Blocked
47%
Avg conflicts / tx
0.72
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,738,276 · 18 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
1w04w05w16w07w18w19w110w212w014w116w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf6c9bf9b…ac02
0x34b655…2a6f
8 touches
6 conflicts
0x7bdccbcd…6bed
0x40c49f…2af0
4 touches
1 conflict
0x84585d11…6ae7
0x34b655…2a6f
4 touches
1 conflict
0x909be59f…0d63
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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 0xf6c9bf9b65…e4ac02
Audit this contract →
← previous block·next block →recent activity