← previous blocknext block →recent activity
Analyzing
Block #80,168,100
20 transactions · 18 stateful · 2026-06-09 14:49:17 UTC
Parallelism
80/100
Blocked
56%
Avg conflicts / tx
1
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,168,100 · 20 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
1w02w13w24w06w27w39w010w111w212w314w316w118w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x179fe783…6945
0xa6afd3…d132
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x90f07a4f…d932
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…002e
0x1b6862…e19c
6 touches
3 conflicts
0x03f9cc30…b46b
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0xdb067026…9eb8
0x69df8a…6292
6 touches
3 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: 0xa6afd386…b0d132
6 conflicts on slot 0x179fe7837f…326945
Audit this contract →
← previous block·next block →recent activity