← previous blocknext block →recent activity
Analyzing
Block #80,241,023
25 transactions · 23 stateful · 2026-06-09 22:55:40 UTC
Parallelism
64/100
Blocked
48%
Avg conflicts / tx
1.32
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #80,241,023 · 25 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
3w04w17w08w19w211w212w218w319w420w521w622w723w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0e5f2a94…4732
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x537e2e5b…c3ab
0x34b655…2a6f
8 touches
6 conflicts
0xa319a588…ef89
0x34b655…2a6f
8 touches
6 conflicts
0x82ded54c…06f6
0x34b655…2a6f
6 touches
3 conflicts
0xb409e204…89ac
0x34b655…2a6f
6 touches
3 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
21 conflicts on slot 0x0e5f2a945b…554732
Audit this contract →
← previous block·next block →recent activity