← previous blocknext block →recent activity
Analyzing
Block #97,683,277
19 transactions · 18 stateful · 2026-08-20 17:28:02 UTC
Parallelism
79/100
Blocked
44%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,683,277 · 19 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
1w02w13w15w06w18w29w310w212w313w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe41626f9…dd93
0x34b655…2a6f
6 touches
3 conflicts
0x1d9276e8…c282
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0002
0x103de0…bb55
4 touches
1 conflict
0x0db691ab…3ee3
0x34b655…2a6f
4 touches
1 conflict
0x26b6e334…9d55
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 0xe41626f95d…d2dd93
Audit this contract →
← previous block·next block →recent activity