← previous blocknext block →recent activity
Analyzing
Block #80,500,615
13 transactions · 9 stateful · 2026-06-11 03:45:38 UTC
Parallelism
85/100
Blocked
22%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,500,615 · 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
1w02w14w05w1
- 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
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x2280ee0b…2543
0x40c49f…2af0
2 touches
0 conflicts
0x331e5dc9…3658
0x40c49f…2af0
2 touches
0 conflicts
0x83c6a7c9…6f6d
0x40c49f…2af0
2 touches
0 conflicts
0xa13eef4a…73a3
0x40c49f…2af0
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