← previous blocknext block →recent activity
Analyzing
Block #80,330,439
21 transactions · 15 stateful · 2026-06-10 08:51:46 UTC
Parallelism
76/100
Blocked
40%
Avg conflicts / tx
0.62
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #80,330,439 · 21 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
2w03w14w09w116w017w118w219w320w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x95847041…2d63
0x34b655…2a6f
7 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xcf30e2fc…ff8f
0x34b655…2a6f
6 touches
3 conflicts
0xd653c5b0…a35a
0x34b655…2a6f
6 touches
3 conflicts
0x445b51c5…0be4
0x34b655…2a6f
4 touches
1 conflict
0x57a080db…7fde
0x34b655…2a6f
4 touches
1 conflict
0x678a8de3…7da5
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity