← previous blocknext block →recent activity
Analyzing
Block #80,104,163
34 transactions · 26 stateful · 2026-06-09 07:43:22 UTC
Parallelism
79/100
Blocked
50%
Avg conflicts / tx
1.32
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #80,104,163 · 34 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w18w010w011w212w313w414w525w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd72a574…e07a
0xa6afd3…d132
12 touches
15 conflicts
0x00000000…003d
0xa6afd3…d132
12 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001c
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002c
0x1b6862…e19c
10 touches
10 conflicts
0xd996735f…8732
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
10 touches
10 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
15 conflicts on slot 0xfd72a57492…01e07a
Audit this contract →
← previous block·next block →recent activity