← previous blocknext block →recent activity
Analyzing
Block #80,776,854
24 transactions · 18 stateful · 2026-06-12 10:28:34 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
1.21
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #80,776,854 · 24 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w27w38w49w511w612w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x6fae99…a56d
16 touches
28 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0xb4b629e6…8d6b
0x065c9d…c394
2 touches
0 conflicts
0xcbe525b5…11ee
0x065c9d…c394
2 touches
0 conflicts
0xe6ae6b92…fded
0x065c9d…c394
2 touches
0 conflicts
0x00000000…003d
0x40c49f…2af0
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: 0x6fae9933…7ba56d
28 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity