← previous blocknext block →recent activity
Analyzing
Block #80,341,257
15 transactions · 9 stateful · 2026-06-10 10:03:53 UTC
Parallelism
87/100
Blocked
11%
Avg conflicts / tx
0.07
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,341,257 · 15 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9f8b48a7…2d5f
0x34b655…2a6f
4 touches
1 conflict
0x1d6cb721…c88c
0x34b655…2a6f
4 touches
1 conflict
0x90f07a4f…d932
0x34b655…2a6f
4 touches
1 conflict
0x54ef8416…dfc5
0x065c9d…c394
2 touches
0 conflicts
0x92ef0885…10a7
0x065c9d…c394
2 touches
0 conflicts
0xadce97a4…34d7
0x065c9d…c394
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
2 touches
0 conflicts
0x5b571ba0…f13a
0x368ee5…7ca4
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 0x9f8b48a753…182d5f
Audit this contract →
← previous block·next block →recent activity