← previous blocknext block →recent activity
Analyzing
Block #80,310,418
13 transactions · 13 stateful · 2026-06-10 06:38:19 UTC
Parallelism
77/100
Blocked
31%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,310,418 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w06w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x158accef…4c74
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xef65bff3…7c9d
0x2a68ba…90c5
4 touches
1 conflict
0x13732567…14b4
0x34b655…2a6f
4 touches
1 conflict
0x89ef0dba…31e2
0x34b655…2a6f
4 touches
1 conflict
0x90f07a4f…d932
0x34b655…2a6f
4 touches
1 conflict
0x94710b77…a921
0x34b655…2a6f
4 touches
1 conflict
0xceba2b98…97b2
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: 0xa6afd386…b0d132
3 conflicts on slot 0x158accef58…554c74
Audit this contract →
← previous block·next block →recent activity