← previous blocknext block →recent activity
Analyzing
Block #80,265,586
40 transactions · 34 stateful · 2026-06-10 01:39:26 UTC
Parallelism
77/100
Blocked
59%
Avg conflicts / tx
1.7
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #80,265,586 · 40 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w17w09w010w111w212w313w414w515w016w119w622w439w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
12 touches
15 conflicts
0x7531e9d9…196d
0xa6afd3…d132
12 touches
15 conflicts
0x00000000…003d
0xa6afd3…d132
12 touches
15 conflicts
0xdf708ee7…1fcf
0xc8689a…ee79
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x40970e69…da50
0x69df8a…6292
10 touches
10 conflicts
0xb5c4826d…bdd6
0x69df8a…6292
10 touches
10 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
28 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity