← previous blocknext block →recent activity
Analyzing
Block #80,631,957
26 transactions · 19 stateful · 2026-06-11 18:22:34 UTC
Parallelism
81/100
Blocked
53%
Avg conflicts / tx
0.62
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #80,631,957 · 26 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
1w02w13w04w25w06w17w28w39w412w315w020w124w125w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xb18bf8…e9f3
10 touches
10 conflicts
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0x394c3833…b4ae
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
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: 0xb18bf8fc…77e9f3
10 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity