← previous blocknext block →recent activity
Analyzing
Block #80,588,519
20 transactions · 13 stateful · 2026-06-11 13:32:23 UTC
Parallelism
90/100
Blocked
23%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,588,519 · 20 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
2w03w16w07w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeef70cb9…5de7
0xea1b8e…c5ec
4 touches
1 conflict
0x8a35acfb…d1a2
0xb327fb…6b13
4 touches
1 conflict
0x8a35acfb…d1a3
0xb327fb…6b13
4 touches
1 conflict
0x455b104f…3960
0xea1b8e…c5ec
4 touches
1 conflict
0xa8abcc19…3d83
0xea1b8e…c5ec
4 touches
1 conflict
0xbc33a929…8b24
0xea1b8e…c5ec
4 touches
1 conflict
0xd8eb2d31…2ac0
0xea1b8e…c5ec
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
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
1 conflict on slot 0xeef70cb93b…ad5de7
Audit this contract →
← previous block·next block →recent activity