← previous blocknext block →recent activity
Analyzing
Block #80,484,290
22 transactions · 18 stateful · 2026-06-11 01:56:52 UTC
Parallelism
77/100
Blocked
39%
Avg conflicts / tx
0.41
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #80,484,290 · 22 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
1w03w06w17w09w010w114w115w119w220w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1d1f14d…3ffb
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0xcb45d9d6…cb84
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x22e0cc1d…ad04
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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
3 conflicts on slot 0xe1d1f14d10…743ffb
Audit this contract →
← previous block·next block →recent activity