← previous blocknext block →recent activity
Analyzing
Block #80,642,473
25 transactions · 18 stateful · 2026-06-11 19:32:41 UTC
Parallelism
88/100
Blocked
11%
Avg conflicts / tx
0.08
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,642,473 · 25 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
13w022w123w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb6ed511f…6b68
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x12309510…0ac2
0x000000…012a
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x160f117d…8e90
0x065c9d…c394
2 touches
0 conflicts
0x429df972…070b
0x065c9d…c394
2 touches
0 conflicts
0x453aa32c…d81f
0x065c9d…c394
2 touches
0 conflicts
0x80b09c55…c4a4
0x065c9d…c394
2 touches
0 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: Perpl
1 conflict on slot 0xb6ed511f4c…ab6b68
Audit this contract →
← previous block·next block →recent activity