← previous blocknext block →recent activity
Analyzing
Block #80,348,403
21 transactions · 15 stateful · 2026-06-10 10:51:27 UTC
Parallelism
76/100
Blocked
33%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #80,348,403 · 21 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
1w05w08w09w116w117w218w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x217bd767…b79e
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x4672a4ae…e965
0x34b655…2a6f
6 touches
3 conflicts
0x84fb2a36…db89
0x34b655…2a6f
6 touches
3 conflicts
0x63e145cf…a2d3
0x34b655…2a6f
6 touches
3 conflicts
0x8c0282ad…0562
0x34b655…2a6f
4 touches
1 conflict
0x8e6a04af…c5e5
0x34b655…2a6f
4 touches
1 conflict
0x9711d99c…3d4c
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
10 conflicts on slot 0x217bd767aa…4fb79e
Audit this contract →
← previous block·next block →recent activity