← previous blocknext block →recent activity
Analyzing
Block #80,407,711
19 transactions · 19 stateful · 2026-06-10 17:26:41 UTC
Parallelism
79/100
Blocked
32%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,407,711 · 19 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
1w02w03w04w15w29w011w114w015w116w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x080ec687…da80
0x34b655…2a6f
6 touches
3 conflicts
0x3d34f2bd…5d63
0x34b655…2a6f
6 touches
3 conflicts
0x0462262d…a368
0x34b655…2a6f
4 touches
1 conflict
0x1b159f3d…9163
0x34b655…2a6f
4 touches
1 conflict
0x1d351a9b…f2dd
0x34b655…2a6f
4 touches
1 conflict
0x1da1c6cb…bb3f
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity