← previous blocknext block →recent activity
Analyzing
Block #80,484,725
19 transactions · 16 stateful · 2026-06-11 01:59:46 UTC
Parallelism
84/100
Blocked
19%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,484,725 · 19 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w16w27w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x217bd767…b79e
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xd1f41160…19da
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x60a8f21c…a647
0x065c9d…c394
3 touches
1 conflict
0xc4606865…3d0c
0x065c9d…c394
3 touches
1 conflict
0xa2867f89…71c2
0x065c9d…c394
3 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
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 0x217bd767aa…4fb79e
Audit this contract →
← previous block·next block →recent activity