← previous blocknext block →recent activity
Analyzing
Block #80,252,890
24 transactions · 19 stateful · 2026-06-10 00:14:45 UTC
Parallelism
79/100
Blocked
37%
Avg conflicts / tx
0.54
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #80,252,890 · 24 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
1w02w13w05w115w118w019w120w221w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xf1597b3b…28f1
0x34b655…2a6f
6 touches
3 conflicts
0xfefd1e1d…5fed
0x34b655…2a6f
6 touches
3 conflicts
0x754c7f04…5673
0x34b655…2a6f
6 touches
3 conflicts
0x85eb1316…bb9e
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x2c506459…5351
0x34b655…2a6f
4 touches
1 conflict
0x3d34f2bd…5d63
0x34b655…2a6f
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity