← previous blocknext block →recent activity
Analyzing
Block #80,311,187
15 transactions · 12 stateful · 2026-06-10 06:43:27 UTC
Parallelism
73/100
Blocked
42%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,311,187 · 15 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
1w03w04w15w27w28w39w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x80afd9d9…57cf
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0xae5e6f9a…2991
0xc8689a…ee79
4 touches
1 conflict
0x21898044…a071
0x065c9d…c394
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0019
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0029
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: Kuru Exchange: Market-MON/USDC
3 conflicts on slot 0x80afd9d9f2…3f57cf
Audit this contract →
← previous block·next block →recent activity