← previous blocknext block →recent activity
Analyzing
Block #80,329,047
9 transactions · 6 stateful · 2026-06-10 08:42:30 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.22
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,329,047 · 9 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x7b9a42f7…7b88
0xa6afd3…d132
4 touches
1 conflict
0xe4afaa2f…3b69
0xa6afd3…d132
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x83cd18cf…6004
0xa6afd3…d132
3 touches
1 conflict
0x7d35d60c…24f6
0x065c9d…c394
2 touches
0 conflicts
0xacad4c2e…ec43
0x065c9d…c394
2 touches
0 conflicts
0x40970e69…da50
0x69df8a…6292
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: 0xa6afd386…b0d132
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity