← previous blocknext block →recent activity
Analyzing
Block #80,300,132
20 transactions · 18 stateful · 2026-06-10 05:29:38 UTC
Parallelism
70/100
Blocked
50%
Avg conflicts / tx
1.15
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #80,300,132 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w410w012w115w216w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdb067026…9eb8
0x69df8a…6292
10 touches
10 conflicts
0x8cf3d245…1d0d
0x69df8a…6292
10 touches
10 conflicts
0xb05cd4f5…73d0
0x69df8a…6292
10 touches
10 conflicts
0xe41f8863…29a4
0xa6afd3…d132
10 touches
10 conflicts
0x7b9a42f7…7b88
0xa6afd3…d132
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
10 touches
10 conflicts
0xef65bff3…7c9d
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: 0x69df8a43…506292
10 conflicts on slot 0xdb06702604…0f9eb8
Audit this contract →
← previous block·next block →recent activity