← previous blocknext block →recent activity
Analyzing
Block #80,631,132
42 transactions · 28 stateful · 2026-06-11 18:17:04 UTC
Parallelism
88/100
Blocked
39%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #80,631,132 · 42 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
1w02w14w15w09w210w111w223w025w027w328w031w438w139w240w341w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x00ddbbf2…4588
0x34b655…2a6f
6 touches
3 conflicts
0x7d42dc8b…fdb6
0x2a68ba…90c5
6 touches
3 conflicts
0x80afd9d9…57cf
0x065c9d…c394
6 touches
3 conflicts
0x21898044…a071
0x065c9d…c394
6 touches
3 conflicts
0xdf7c1166…7bff
0x065c9d…c394
5 touches
3 conflicts
0xc52ac4e6…986d
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0004
0x63e48b…53f2
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