← previous blocknext block →recent activity
Analyzing
Block #80,250,987
14 transactions · 12 stateful · 2026-06-10 00:02:05 UTC
Parallelism
64/100
Blocked
33%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #80,250,987 · 14 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
1w02w13w24w35w4
- 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
0x8876d94c…8435
0x2a68ba…90c5
2 touches
0 conflicts
0x404314de…df1a
0x3bd359…433a
2 touches
0 conflicts
0x5d82c9b5…004c
0x3bd359…433a
2 touches
0 conflicts
0xb98b9e9d…a785
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0004
0x5afd3e…7620
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