← previous blocknext block →recent activity
Analyzing
Block #80,745,647
34 transactions · 22 stateful · 2026-06-12 07:00:35 UTC
Parallelism
85/100
Blocked
45%
Avg conflicts / tx
0.74
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #80,745,647 · 34 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w06w17w28w09w110w211w314w419w220w324w025w128w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x6fae99…a56d
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x52d65d97…1c96
0xa6afd3…d132
8 touches
6 conflicts
0x9e20cccf…19cc
0xa6afd3…d132
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x1e78f72b…5df2
0x40c49f…2af0
4 touches
1 conflict
0x342fbbca…d443
0x40c49f…2af0
4 touches
1 conflict
0xc6a4504e…5537
0x40c49f…2af0
4 touches
1 conflict
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: 0x6fae9933…7ba56d
10 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity