← previous blocknext block →recent activity
Analyzing
Block #80,653,903
18 transactions · 14 stateful · 2026-06-11 20:48:54 UTC
Parallelism
56/100
Blocked
50%
Avg conflicts / tx
1.56
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #80,653,903 · 18 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
4w05w16w27w38w49w510w611w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x6fae99…a56d
16 touches
28 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0x0d704c3a…c75a
0x34b655…2a6f
2 touches
0 conflicts
0x3746adc0…cbc6
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
0x34b655…2a6f
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