← previous blocknext block →recent activity
Analyzing
Block #80,653,583
17 transactions · 11 stateful · 2026-06-11 20:46:46 UTC
Parallelism
76/100
Blocked
36%
Avg conflicts / tx
0.41
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,653,583 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w07w18w29w311w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x6fae99…a56d
8 touches
6 conflicts
0x33fd450f…2d86
0xa6afd3…d132
4 touches
1 conflict
0x11b69a7e…334e
0xee8c0e…1242
4 touches
1 conflict
0xef65bff3…7c9d
0x2a68ba…90c5
4 touches
1 conflict
0x846f2172…fd54
0x0555e3…2b9c
2 touches
0 conflicts
0x8edd456e…c7e3
0x0555e3…2b9c
2 touches
0 conflicts
0x09beabbc…065c
0x188d58…ea8e
2 touches
0 conflicts
0x09beabbc…065e
0x188d58…ea8e
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
6 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity