← previous blocknext block →recent activity
Analyzing
Block #80,167,292
14 transactions · 12 stateful · 2026-06-09 14:43:53 UTC
Parallelism
79/100
Blocked
25%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,167,292 · 14 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
1w02w14w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeef70cb9…5de7
0xea1b8e…c5ec
4 touches
1 conflict
0xbc33a929…8b24
0xea1b8e…c5ec
4 touches
1 conflict
0xd8eb2d31…2ac0
0xea1b8e…c5ec
4 touches
1 conflict
0x35256c50…c721
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x455b104f…3960
0xea1b8e…c5ec
4 touches
1 conflict
0x6a2a02d3…df31
0x065c9d…c394
3 touches
1 conflict
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: LeverUp: LeverUp
1 conflict on slot 0xeef70cb93b…ad5de7
Audit this contract →
← previous block·next block →recent activity