← previous blocknext block →recent activity
Analyzing
Block #80,329,134
22 transactions · 19 stateful · 2026-06-10 08:43:05 UTC
Parallelism
73/100
Blocked
42%
Avg conflicts / tx
0.86
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #80,329,134 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w06w17w29w010w112w013w114w215w316w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa743c8dd…ebf2
0x788571…8888
12 touches
15 conflicts
0x771a3650…01cd
0x3bd359…433a
12 touches
15 conflicts
0x00000000…0001
0x24b18e…3301
12 touches
15 conflicts
0x00000000…0000
0x24b18e…3301
12 touches
15 conflicts
0x797464db…e15a
0x788571…8888
12 touches
15 conflicts
0x00bac013…a28c
0xfd44b3…00d1
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x21898044…a071
0x065c9d…c394
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: 0x788571e0…f48888
15 conflicts on slot 0xa743c8dd91…28ebf2
Audit this contract →
← previous block·next block →recent activity