← previous blocknext block →recent activity
Analyzing
Block #80,777,115
60 transactions · 16 stateful · 2026-06-12 10:30:19 UTC
Parallelism
93/100
Blocked
31%
Avg conflicts / tx
0.13
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,777,115 · 60 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
2w013w020w146w249w354w156w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf6476f21…3580
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x482f8413…133c
0x34b655…2a6f
4 touches
1 conflict
0x94710b77…a921
0x34b655…2a6f
4 touches
1 conflict
0x952f45ec…c54b
0x34b655…2a6f
4 touches
1 conflict
0xac808a27…82db
0x34b655…2a6f
4 touches
1 conflict
0xaf78779d…317d
0x34b655…2a6f
4 touches
1 conflict
0xb2440e98…1efa
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
6 conflicts on slot 0xf6476f21e7…f83580
Audit this contract →
← previous block·next block →recent activity