← previous blocknext block →recent activity
Analyzing
Block #80,166,415
29 transactions · 22 stateful · 2026-06-09 14:38:03 UTC
Parallelism
76/100
Blocked
41%
Avg conflicts / tx
0.66
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #80,166,415 · 29 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
1w02w19w010w111w212w313w116w125w026w427w528w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8af21051…95c5
0x34b655…2a6f
8 touches
6 conflicts
0xcdc8b4bb…7bce
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x90f07a4f…d932
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001e
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002e
0x1b6862…e19c
4 touches
1 conflict
0x083a8763…5a7e
0x1b6862…e19c
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 0x8af210517e…8295c5
Audit this contract →
← previous block·next block →recent activity