← previous blocknext block →recent activity
Analyzing
Block #80,654,095
37 transactions · 23 stateful · 2026-06-11 20:50:11 UTC
Parallelism
89/100
Blocked
52%
Avg conflicts / tx
0.51
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,654,095 · 37 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
1w02w03w14w15w27w08w117w018w119w220w021w122w223w333w034w135w236w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x90f07a4f…d932
0x34b655…2a6f
6 touches
3 conflicts
0xb0e9898d…42c2
0xa6afd3…d132
6 touches
3 conflicts
0xc38151f2…2bcb
0xc8689a…ee79
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x40970e69…da50
0x69df8a…6292
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity