← previous blocknext block →recent activity
Analyzing
Block #80,233,153
14 transactions · 9 stateful · 2026-06-09 22:03:15 UTC
Parallelism
79/100
Blocked
22%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,233,153 · 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
3w04w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc2fc05e8…524f
0xea1b8e…c5ec
6 touches
3 conflicts
0x9560013d…8caf
0xfd44b3…00d1
6 touches
3 conflicts
0x00bac013…a28c
0xfd44b3…00d1
6 touches
3 conflicts
0xfecd05e7…2970
0xea1b8e…c5ec
6 touches
3 conflicts
0xfecd05e7…296f
0xea1b8e…c5ec
6 touches
3 conflicts
0xd8eb2d31…2ac0
0xea1b8e…c5ec
6 touches
3 conflicts
0xc2fc05e8…5252
0xea1b8e…c5ec
6 touches
3 conflicts
0x00000000…0099
0xaa3145…feec
4 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
3 conflicts on slot 0xc2fc05e867…60524f
Audit this contract →
← previous block·next block →recent activity