← previous blocknext block →recent activity
Analyzing
Block #80,314,504
13 transactions · 10 stateful · 2026-06-10 07:05:35 UTC
Parallelism
85/100
Blocked
20%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,314,504 · 13 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
1w06w010w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb04d17a0…10e8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x158accef…4c74
0xa6afd3…d132
4 touches
1 conflict
0xcdacbdc7…dd44
0xa6afd3…d132
3 touches
1 conflict
0x4139c1b0…7457
0x34b655…2a6f
2 touches
0 conflicts
0x6e9e139e…cc61
0x34b655…2a6f
2 touches
0 conflicts
0x7e1c758b…2f47
0x34b655…2a6f
2 touches
0 conflicts
0x90f07a4f…d932
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
1 conflict on slot 0xb04d17a0fe…4810e8
Audit this contract →
← previous block·next block →recent activity