← previous blocknext block →recent activity
Analyzing
Block #80,287,357
59 transactions · 47 stateful · 2026-06-10 04:04:29 UTC
Parallelism
70/100
Blocked
77%
Avg conflicts / tx
3.39
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #80,287,357 · 59 txs across 18 waves · depth 18
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
wave w16
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w19w010w011w112w213w314w415w516w617w718w819w922w1039w1241w1343w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
24 touches
66 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
22 touches
55 conflicts
0x00000000…003d
0xa6afd3…d132
18 touches
36 conflicts
0x90f07a4f…d932
0x34b655…2a6f
16 touches
28 conflicts
0x8cf3d245…1d0d
0x69df8a…6292
16 touches
28 conflicts
0xef65bff3…7c9d
0x2a68ba…90c5
16 touches
28 conflicts
0x89ef0dba…31e2
0x34b655…2a6f
16 touches
28 conflicts
0x40970e69…da50
0x69df8a…6292
16 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: Kuru Exchange: MarginAccount
66 conflicts on slot 0x13a54fa2d3…a35ae3
Audit this contract →
← previous block·next block →recent activity