← previous blocknext block →recent activity
Analyzing
Block #80,760,699
33 transactions · 8 stateful · 2026-06-12 08:40:53 UTC
Parallelism
85/100
Blocked
63%
Avg conflicts / tx
0.36
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #80,760,699 · 33 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
2w010w112w213w324w430w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf6476f21…3580
0x34b655…2a6f
10 touches
10 conflicts
0xfcfb570f…cf1c
0x34b655…2a6f
8 touches
6 conflicts
0x4fe4d51f…835a
0x34b655…2a6f
8 touches
6 conflicts
0x9a3068dd…18f0
0x34b655…2a6f
8 touches
6 conflicts
0xaa7dcca1…6422
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…641e
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…641f
0x34b655…2a6f
8 touches
6 conflicts
0xf6884b1c…8b7f
0x34b655…2a6f
8 touches
6 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: Perpl
10 conflicts on slot 0xf6476f21e7…f83580
Audit this contract →
← previous block·next block →recent activity