← previous blocknext block →recent activity
Analyzing
Block #80,264,771
12 transactions · 11 stateful · 2026-06-10 01:34:00 UTC
Parallelism
83/100
Blocked
9%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,264,771 · 12 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
2w03w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x36d366fe…7adc
0xa6afd3…d132
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x1e2f3c73…6e0e
0x065c9d…c394
2 touches
0 conflicts
0x5ed87b8a…f080
0x065c9d…c394
2 touches
0 conflicts
0x7c7c29e6…1b97
0x065c9d…c394
2 touches
0 conflicts
0x8df9b557…7edf
0x065c9d…c394
2 touches
0 conflicts
0x91f8efcd…ed26
0x065c9d…c394
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