← previous blocknext block →recent activity
Analyzing
Block #80,328,768
24 transactions · 20 stateful · 2026-06-10 08:40:39 UTC
Parallelism
83/100
Blocked
45%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,328,768 · 24 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
1w02w03w15w16w213w014w115w216w318w019w120w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa743c8dd…ebf2
0x788571…8888
8 touches
6 conflicts
0x00000000…0000
0x24b18e…3301
8 touches
6 conflicts
0x00000000…0001
0x24b18e…3301
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x771a3650…01cd
0x3bd359…433a
8 touches
6 conflicts
0x797464db…e15a
0x788571…8888
8 touches
6 conflicts
0x217bd767…b79e
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0029
0x1b6862…e19c
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: 0x788571e0…f48888
6 conflicts on slot 0xa743c8dd91…28ebf2
Audit this contract →
← previous block·next block →recent activity