← previous blocknext block →recent activity
Analyzing
Block #80,251,003
22 transactions · 17 stateful · 2026-06-10 00:02:12 UTC
Parallelism
77/100
Blocked
41%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #80,251,003 · 22 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
1w02w14w15w16w07w18w29w310w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9f4e12e3…21c7
0x336ed4…c59c
10 touches
10 conflicts
0x00000000…000a
0x90c374…be45
10 touches
10 conflicts
0x00000000…000b
0x90c374…be45
10 touches
10 conflicts
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x5eb6e179…f529
0x065c9d…c394
3 touches
1 conflict
0x07119d6a…27b6
0xd32edf…ff58
3 touches
1 conflict
0x00000000…001f
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002f
0x1b6862…e19c
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: 0x336ed437…cfc59c
10 conflicts on slot 0x9f4e12e393…0a21c7
Audit this contract →
← previous block·next block →recent activity