← previous blocknext block →recent activity
Analyzing
Block #80,330,257
22 transactions · 18 stateful · 2026-06-10 08:50:34 UTC
Parallelism
68/100
Blocked
39%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #80,330,257 · 22 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w113w015w116w217w318w419w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x7b9a42f7…7b88
0xa6afd3…d132
4 touches
1 conflict
0x81e1f4e8…08d7
0x34b655…2a6f
4 touches
1 conflict
0x94a3fb3f…7515
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xb409e204…89ac
0x34b655…2a6f
4 touches
1 conflict
0xb8228d38…3953
0x34b655…2a6f
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
21 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity