← previous blocknext block →recent activity
Analyzing
Block #80,692,290
13 transactions · 11 stateful · 2026-06-12 01:04:45 UTC
Parallelism
77/100
Blocked
27%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,692,290 · 13 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
4w05w17w09w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xbaeed020…92f8
0x34b655…2a6f
4 touches
1 conflict
0xc2fc05e8…524f
0xea1b8e…c5ec
4 touches
1 conflict
0xc2fc05e8…5252
0xea1b8e…c5ec
4 touches
1 conflict
0xd8eb2d31…2ac0
0xea1b8e…c5ec
4 touches
1 conflict
0xeef70cb9…5de7
0xea1b8e…c5ec
4 touches
1 conflict
0xfecd05e7…296f
0xea1b8e…c5ec
4 touches
1 conflict
0xfecd05e7…2970
0xea1b8e…c5ec
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: Perpl
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity