← previous blocknext block →recent activity
Analyzing
Block #80,340,184
22 transactions · 15 stateful · 2026-06-10 09:56:43 UTC
Parallelism
73/100
Blocked
33%
Avg conflicts / tx
0.64
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #80,340,184 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w116w017w218w319w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xf6d214b0…8abe
0x34b655…2a6f
4 touches
1 conflict
0x056ec16c…55b9
0x34b655…2a6f
4 touches
1 conflict
0x379a09c4…259b
0x34b655…2a6f
4 touches
1 conflict
0x5ba4db2b…2f04
0x34b655…2a6f
4 touches
1 conflict
0x89ef0dba…31e2
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