← previous blocknext block →recent activity
Analyzing
Block #80,822,475
24 transactions · 17 stateful · 2026-06-12 15:32:50 UTC
Parallelism
92/100
Blocked
12%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,822,475 · 24 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w114w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9a3068dd…18f0
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f1
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x6fae99…a56d
4 touches
1 conflict
0xf6884b1c…8b7f
0x34b655…2a6f
3 touches
1 conflict
0x6cda3f80…809b
0x34b655…2a6f
3 touches
1 conflict
0x7d42dc8b…fdb6
0x2a68ba…90c5
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 0x9a3068dd84…9918f0
Audit this contract →
← previous block·next block →recent activity