← previous blocknext block →recent activity
Analyzing
Block #80,309,716
19 transactions · 13 stateful · 2026-06-10 06:33:36 UTC
Parallelism
84/100
Blocked
38%
Avg conflicts / tx
0.26
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,309,716 · 19 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w16w17w08w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xc824469a…641c
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x7b9a42f7…7b88
0xa6afd3…d132
4 touches
1 conflict
0x4616c45f…3485
0xd32edf…ff58
3 touches
1 conflict
0x00000000…0019
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0029
0x1b6862…e19c
2 touches
0 conflicts
0xba5743c7…21c0
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: MarginAccount
1 conflict on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity