← previous blocknext block →recent activity
Analyzing
Block #86,053,199
34 transactions · 23 stateful · 2026-07-06 20:59:57 UTC
Parallelism
79/100
Blocked
39%
Avg conflicts / tx
0.5
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,053,199 · 34 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w17w210w311w415w327w528w029w130w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92d610a6…9a40
0x2a68ba…90c5
10 touches
10 conflicts
0x914f55fc…7d81
0x065c9d…c394
9 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0xcc8faac2…c766
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0007
0x8f889b…868c
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x01e7b865…6e6d
0x188d58…ea8e
4 touches
1 conflict
0xdd70bea3…1ffe
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
10 conflicts on slot 0x92d610a6f9…379a40
Audit this contract →
← previous block·next block →recent activity