← previous blocknext block →recent activity
Analyzing
Block #80,252,344
13 transactions · 12 stateful · 2026-06-10 00:11:08 UTC
Parallelism
85/100
Blocked
25%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,252,344 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7f9f6049…a86a
0x065c9d…c394
4 touches
1 conflict
0x21898044…a071
0x065c9d…c394
4 touches
1 conflict
0xc0621383…7d3f
0x065c9d…c394
3 touches
1 conflict
0x22e28930…f754
0x065c9d…c394
3 touches
1 conflict
0x80afd9d9…57cf
0x065c9d…c394
2 touches
0 conflicts
0xfe7cc0d6…5994
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
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
1 conflict on slot 0x7f9f604953…e3a86a
Audit this contract →
← previous block·next block →recent activity