← previous blocknext block →recent activity
Analyzing
Block #80,635,015
28 transactions · 14 stateful · 2026-06-11 18:42:59 UTC
Parallelism
89/100
Blocked
29%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,635,015 · 28 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
1w02w13w04w17w013w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf6476f21…3580
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xb18bf8…e9f3
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xaf498679…7732
0x34b655…2a6f
4 touches
1 conflict
0xb54bf2aa…563e
0x34b655…2a6f
4 touches
1 conflict
0xc5e2762e…eb2d
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x00ea5f69…5cdf
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
3 conflicts on slot 0xf6476f21e7…f83580
Audit this contract →
← previous block·next block →recent activity