← previous blocknext block →recent activity
Analyzing
Block #80,101,922
33 transactions · 26 stateful · 2026-06-09 07:28:27 UTC
Parallelism
51/100
Blocked
73%
Avg conflicts / tx
2.67
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #80,101,922 · 33 txs across 16 waves · depth 16
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
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w312w013w114w215w316w417w518w619w720w821w924w327w1031w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb87d7c5e…3b45
0x34b655…2a6f
20 touches
45 conflicts
0x90f07a4f…d932
0x34b655…2a6f
20 touches
45 conflicts
0x8db1e0f2…2fcf
0x34b655…2a6f
18 touches
36 conflicts
0xc38151f2…2bcb
0xc8689a…ee79
16 touches
28 conflicts
0x7895a98c…bbfa
0x34b655…2a6f
16 touches
28 conflicts
0x908d4442…2c4b
0x34b655…2a6f
16 touches
28 conflicts
0xedb848fe…6534
0x34b655…2a6f
16 touches
28 conflicts
0xd8e48935…a5a9
0x34b655…2a6f
15 touches
28 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
45 conflicts on slot 0xb87d7c5efc…0d3b45
Audit this contract →
← previous block·next block →recent activity