← previous blocknext block →recent activity
Analyzing
Block #81,625,960
29 transactions · 28 stateful · 2026-06-16 08:45:24 UTC
Parallelism
66/100
Blocked
64%
Avg conflicts / tx
2.24
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #81,625,960 · 29 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w05w16w27w19w210w311w412w513w614w616w717w819w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x202c03eb…cf33
0xa6afd3…d132
8 touches
6 conflicts
0x5581d709…ab77
0x2a68ba…90c5
6 touches
3 conflicts
0x897df0ee…b0c5
0x40c49f…2af0
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0xe5e7089a…fb91
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: Kuru Exchange: MarginAccount
36 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity