← previous blocknext block →recent activity
Analyzing
Block #79,116,201
30 transactions · 26 stateful · 2026-06-04 17:40:30 UTC
Parallelism
73/100
Blocked
46%
Avg conflicts / tx
0.93
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #79,116,201 · 30 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w05w16w07w18w29w310w411w517w418w619w524w128w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
10 touches
10 conflicts
0x80afd9d9…57cf
0x065c9d…c394
8 touches
6 conflicts
0xe8b0ec22…bde4
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x898d22cb…ed6c
0x065c9d…c394
5 touches
3 conflicts
0x00000000…0000
0x63e48b…53f2
4 touches
1 conflict
0x00000000…0003
0x63e48b…53f2
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
10 conflicts on slot 0x13a54fa2d3…a35ae3
Audit this contract →
← previous block·next block →recent activity