← previous blocknext block →recent activity
Analyzing
Block #80,639,977
22 transactions · 19 stateful · 2026-06-11 19:16:05 UTC
Parallelism
82/100
Blocked
32%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,639,977 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w16w27w38w09w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xb18bf8…e9f3
8 touches
6 conflicts
0x22e0cc1d…ad04
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xe5a10916…8ad0
0xa6afd3…d132
4 touches
1 conflict
0xcb258d81…b846
0xa6afd3…d132
3 touches
1 conflict
0x00000000…0005
0x0594c7…a3be
2 touches
0 conflicts
0xa5d3ee6e…8583
0x0594c7…a3be
2 touches
0 conflicts
0xb5657f9b…80aa
0x0594c7…a3be
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: 0xb18bf8fc…77e9f3
6 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity