← previous blocknext block →recent activity
Analyzing
Block #80,613,346
12 transactions · 9 stateful · 2026-06-11 16:18:13 UTC
Parallelism
83/100
Blocked
22%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,613,346 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x90f07a4f…d932
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x20823c5b…0a79
0x065c9d…c394
2 touches
0 conflicts
0x2666f077…4b82
0x065c9d…c394
2 touches
0 conflicts
0x3d91c172…da6e
0x065c9d…c394
2 touches
0 conflicts
0x5abdcfa2…b74a
0x065c9d…c394
2 touches
0 conflicts
0x8614e3a3…ba96
0x065c9d…c394
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: Perpl
1 conflict on slot 0x90f07a4ff9…b3d932
Audit this contract →
← previous block·next block →recent activity