← previous blocknext block →recent activity
Analyzing
Block #86,350,266
22 transactions · 19 stateful · 2026-07-08 06:03:03 UTC
Parallelism
68/100
Blocked
53%
Avg conflicts / tx
0.95
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,350,266 · 22 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
1w02w13w24w06w17w38w412w513w615w416w017w120w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92d610a6…9a40
0x2a68ba…90c5
8 touches
6 conflicts
0xcc8faac2…c766
0x065c9d…c394
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x6b903198…1d2f
0x065c9d…c394
5 touches
3 conflicts
0x5b4cd072…c461
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x614b85…a284
4 touches
1 conflict
0x00000000…0002
0x614b85…a284
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 0x92d610a6f9…379a40
Audit this contract →
← previous block·next block →recent activity