← previous blocknext block →recent activity
Analyzing
Block #80,676,950
14 transactions · 12 stateful · 2026-06-11 23:22:27 UTC
Parallelism
64/100
Blocked
42%
Avg conflicts / tx
0.36
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #80,676,950 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w36w412w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x9d3f2124…725b
0x2a68ba…90c5
2 touches
1 conflict
0xb182933f…46ed
0x754704…b603
2 touches
1 conflict
0x683e0c5f…7929
0x065c9d…c394
2 touches
0 conflicts
0xd2555f31…1970
0x065c9d…c394
2 touches
0 conflicts
0x44ad89ba…cf83
0x23c26b…7777
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity