← previous blocknext block →recent activity
Analyzing
Block #80,327,741
25 transactions · 21 stateful · 2026-06-10 08:33:49 UTC
Parallelism
84/100
Blocked
38%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,327,741 · 25 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
6w07w18w09w111w212w215w016w118w322w023w224w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x217bd767…b79e
0x34b655…2a6f
8 touches
6 conflicts
0x158accef…4c74
0xa6afd3…d132
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x25d30ad6…a8ec
0x34b655…2a6f
4 touches
1 conflict
0x8c0282ad…0562
0x34b655…2a6f
4 touches
1 conflict
0x90f07a4f…d932
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
6 conflicts on slot 0x217bd767aa…4fb79e
Audit this contract →
← previous block·next block →recent activity