← previous blocknext block →recent activity
Analyzing
Block #80,234,469
17 transactions · 14 stateful · 2026-06-09 22:12:03 UTC
Parallelism
76/100
Blocked
29%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,234,469 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w29w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7d42dc8b…fdb6
0x2a68ba…90c5
8 touches
6 conflicts
0x21898044…a071
0x065c9d…c394
6 touches
3 conflicts
0x74ce3ffa…7d9b
0x065c9d…c394
5 touches
3 conflicts
0x67f96963…c350
0xdd0a93…ece5
4 touches
1 conflict
0x78ae17f2…53be
0x000000…012a
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x28e527c8…c6f2
0x3bd359…433a
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: Kuru Exchange: MarginAccount
6 conflicts on slot 0x7d42dc8b22…fefdb6
Audit this contract →
← previous block·next block →recent activity