← previous blocknext block →recent activity
Analyzing
Block #79,114,790
34 transactions · 24 stateful · 2026-06-04 17:31:03 UTC
Parallelism
85/100
Blocked
46%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #79,114,790 · 34 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w16w27w08w09w110w214w017w320w222w324w425w327w130w031w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x518f2037…e422
0xa6afd3…d132
6 touches
3 conflicts
0x4ef5c646…5af8
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x40970e69…da50
0x69df8a…6292
4 touches
1 conflict
0x8cf3d245…1d0d
0x69df8a…6292
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 0x13a54fa2d3…a35ae3
Audit this contract →
← previous block·next block →recent activity