← previous blocknext block →recent activity
Analyzing
Block #80,826,680
18 transactions · 11 stateful · 2026-06-12 16:00:52 UTC
Parallelism
78/100
Blocked
27%
Avg conflicts / tx
0.22
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,826,680 · 18 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
2w05w18w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf6476f21…3580
0x34b655…2a6f
6 touches
3 conflicts
0x5b0aabe4…be02
0x34b655…2a6f
4 touches
1 conflict
0x5c025cb8…bc9c
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0498c5a0…65c3
0x34b655…2a6f
4 touches
1 conflict
0x5a19ef35…dc70
0x34b655…2a6f
4 touches
1 conflict
0x4ec9ff52…e6f7
0x34b655…2a6f
2 touches
0 conflicts
0x4f3a6b4a…3819
0x34b655…2a6f
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
3 conflicts on slot 0xf6476f21e7…f83580
Audit this contract →
← previous block·next block →recent activity