← previous blocknext block →recent activity
Analyzing
Block #80,330,303
46 transactions · 39 stateful · 2026-06-10 08:50:52 UTC
Parallelism
70/100
Blocked
69%
Avg conflicts / tx
2.54
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #80,330,303 · 46 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w16w27w09w110w211w312w413w514w615w716w717w829w831w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf412c531…d397
0xa6afd3…d132
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
16 touches
28 conflicts
0x00000000…003d
0xa6afd3…d132
14 touches
21 conflicts
0xb05cd4f5…73d0
0x69df8a…6292
12 touches
15 conflicts
0x1c7763f6…89be
0x34b655…2a6f
12 touches
15 conflicts
0x90f07a4f…d932
0x34b655…2a6f
12 touches
15 conflicts
0x8cf3d245…1d0d
0x69df8a…6292
12 touches
15 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: 0xa6afd386…b0d132
28 conflicts on slot 0xf412c53157…a8d397
Audit this contract →
← previous block·next block →recent activity